Detection and protection of data in API calls

ABSTRACT

Aspects of the present disclosure relate to detecting and protecting a class of data in an API call including determining a plurality of field names and identifying a field name to search for in the data. The technique further includes generating, in response to the identifying the field name, an encryption key and an expiration, wherein the encryption key is configured to encrypt the data. The technique also comprises encrypting the data, sending the API call to an application server, wherein the application server is configured to process the API call. The technique also includes receiving, from the application server, a request for the encryption key and validating that the encryption key has not expired. The technique also includes, sending, in response to being valid, the encryption key to the application server, and storing, in a database, a set of usage data associated with the encryption key.

BACKGROUND

The present disclosure relates to data protection, and, morespecifically, to protecting personal data during an individualapplication program interface (API) call.

Information privacy (e.g., data privacy or data protection) is therelationship between the collection and dissemination of data, thetechnology used to collect and disseminate data, the expectation ofprivacy of data, and the legal and political issues that dictate what isconsidered to be private data. Privacy concerns arise whenever personalidentifiable information or other personal sensitive information iscollected, stored, used, or otherwise disseminated.

SUMMARY

Disclosed is a computer-implemented method comprising invoking an APIcall. The method also comprises, determining, in the API call, aplurality of field names, and identifying a first field name to searchfor a first instance of sensitive information. The method alsocomprises, identifying a first instance of sensitive information in thefirst field name, wherein the first instance of sensitive information isidentified by pattern matching. The method also comprises, generating,in response to the identifying the first instance of sensitiveinformation, a first encryption key and a first expiration, wherein thefirst encryption key is configured to encrypt the first instance ofsensitive information. The method also comprises, encrypting the firstinstance of sensitive information, sending the API call to anapplication server, wherein the application server is configured toprocess the API call. The method also comprises, receiving at a firsttime, from the application server, a request for the first encryptionkey, and validating that the first time is before the first expiration.The method also comprises, sending, in response to determining theencryption key is valid, the first encryption key to the applicationserver, and storing, in a usage database, a set of usage data associatedwith the first encryption key. Further aspects of the present disclosureare directed to systems and computer program products containingfunctionality consistent with the method described above.

The present Summary is not intended to illustrate each aspect of, everyimplementation of, and/or every embodiment of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings included in the present application are incorporated into,and form part of, the specification. They illustrate embodiments of thepresent disclosure and, along with the description, serve to explain theprinciples of the disclosure. The drawings are only illustrative ofcertain embodiments and do not limit the disclosure.

FIG. 1 illustrates a functional diagram of a computing environmentsuitable for operation of a sensitive information manager in accordancewith various embodiments of the present disclosure.

FIG. 2 is a flowchart depicting an example method for detecting andprotecting sensitive information, in accordance with various embodimentsof the present disclosure.

FIG. 3 illustrates a block diagram of an example sensitive informationmanager, in accordance with various embodiments of the presentdisclosure.

FIG. 4 illustrates a cloud computing environment in accordance with someembodiments of the present disclosure.

FIG. 5 depicts abstraction model layers in accordance with someembodiments of the present disclosure.

While the present disclosure is amenable to various modifications andalternative forms, specifics thereof have been shown by way of examplein the drawings and will be described in detail. It should beunderstood, however, that the intention is not to limit the presentdisclosure to the particular embodiments described. On the contrary, theintention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the present disclosure.

DETAILED DESCRIPTION

Aspects of the current disclosure relate to data protection, and, morespecifically, to protecting personal data during an individual API call.Aspects of the present disclosure may be better appreciated in light ofthe aforementioned applications.

Information privacy (e.g., data privacy or data protection) is therelationship between the collection and dissemination of data, thetechnology used to collect and disseminate data, the public'sexpectation of privacy of the data, and the legal and political issuesthat dictate what is considered to be private data. Privacy concernsarise whenever personally identifiable information or other sensitiveinformation is collected, stored, used, or otherwise disseminated.

Many new and developing technologies require users to share theirpersonal information to adequately utilize the offered services. Forexample, online shopping can ask a user to provide a shipping addressfor purchased goods. In some cases, the company (application owner,processor, data processor) that first collects the personal informationtransfers the data to third parties to assist in completion of an APIcall. For example, a bank may send data about a customer to a thirdparty to request a credit score of the customer.

The amount of personal data that is used and shared by thesetechnologies is rapidly increasing. The rapid increase has led to newconcerns relating to the protection of privacy and the prevention ofmisuse of the personal information of technology users. Users of thesetechnologies are inquiring as to how and when data they provide is beingused, and the methods used to secure their personal information.

Breaches of personal data can happen in a variety of ways. Those thatgarner the most attention are large scale breaches, often caused byincorrect technical configurations or lack of due care on an industrialscale. Embodiments of the present disclosure recognize information canbe compromised on a small scale. Small scale breaches may be harder todetect or may not garner the same amount of outside attention as largebreaches. However, small scale breaches can have equally negativeconsequences to the victim and to the entities responsible for thebreach.

Embodiments of the current disclosure can detect and protect sensitivedata at the transaction level. One example of a transaction can be arequest through an API or API call. In some embodiments, the API call isdivided into one or more field names or fields. A field name is aheading/term descriptive of the data contained under that field name.For example, a field name can be “Customer Number” and the datacontained under the field name can be 54321.

The term personally identifiable information (PII) may cover any type ofinformation that can be used to identify an individual based on thatinformation. Some examples of PII include social security numbers,European identifiers, drivers license numbers, and the like. Sensitivepersonal information (SPI) refers to information that does not identifyan individual but is related to an individual and communicatesinformation that is private or could potentially harm the individual.Examples of SPI include biometric data, genetic information, gender,trade union memberships, sexual orientation, and the like. Sensitiveinformation (SI) or sensitive data refers to any data that is eitherPII, SPI, and/or other data that may be considered confidential.

Various embodiments of the present disclosure can identify and protectdata that should be kept secure. In some embodiments, the sensitive datais identified in an API call or other transaction request. An API can beorganized by field names. In some embodiments, the data contained in thefield names can be generalized then examined for data that should besecure. In some embodiments, a key, such as an encryption key, can begenerated and the data secured prior to sending the data over anynetwork where it could potentially be compromised. The key can begenerated by the device that generates the API call or by a separatedevice (or module, program, etc.). In some embodiments, the key is onlyvalid under a specific set of conditions (e.g. before an expiration,etc.) In some embodiments, the target of the API call can then requestthe key to decrypt the data. In some embodiments, the actions related tothe key (e.g. generation, distribution, etc.) are recorded, and can bedelivered to the data owner.

In some embodiments, pattern identification is used to detect andprotect sensitive information in API calls. In some embodiments, asolicitor service can be used to detect and protect sensitiveinformation in API calls. The solicitor service can be a Key ManagementServer (KMS) as an example. This can increase the efficiency ofcomputing systems by only encrypting specific data, rather than all ofthe data in an API call.

In some embodiments, encryption may be used to protect API calls withsensitive information. In some embodiments, the encryption and/ordecryption can be time based. In some embodiments, the solicitor servicecan implement the encryption and use different security settings such asBlock All principle. The Block All principle is when all access to theencryption is blocked unless a set of conditions are met. In someembodiments, the conditions to allow access to an encryption key can bethat (1) the data processor is explicitly permitted to retrieve the key,and that (2) the expiration has not passed.

The aforementioned advantages are example advantages, and embodimentsexist that can contain all, some, or none of the aforementionedadvantages while remaining within the spirit and scope of the presentdisclosure.

Referring now to various embodiments of the disclosure in more detail,FIG. 1 is a representation of a computing environment, generally labeled100, that is capable of running a sensitive information (SI) manager105, in accordance with one or more embodiments of the presentdisclosure. Many modifications to the depicted environment may be madeby those skilled in the art without departing from the scope of thedisclosure as recited by the claims.

Computing environment 100 includes computer system 110, applicationserver 115, security module 120, and network 125. Network 125 can be,for example, a telecommunications network, a local area network (LAN), awide area network (WAN), such as the Internet, or a combination of thethree, and can include wired, wireless, or fiber optic connections.Network 125 may include one or more wired and/or wireless networks thatare capable of receiving and transmitting data, voice, and/or videosignals, including multimedia signals that include voice, data, andvideo information. In general, network 125 may be any combination ofconnections and protocols that will support communications betweencomputer system 110, application server 115, security module 120, andother computing devices (not shown) within computing environment 100.

Computer system 110 can be a standalone computing device, a managementserver, a web server, a mobile computing device, or any other electronicdevice or computing system capable of receiving, sending, and processingdata. In other embodiments, computer system 110 can represent a servercomputing system utilizing multiple computers as a server system, suchas in a cloud computing environment. In some embodiments, computersystem 110 represents a computing system utilizing clustered computersand components (e.g., database server computers, application servercomputers, etc.) that act as a single pool of seamless resources whenaccessed within computing environment 100. Computer system 110 includesSI manager 105. Computer system 110 may include internal and externalhardware components, as depicted and described in further detail withrespect to FIG. 3.

In some embodiments, computer system 110 invokes an API call. In someembodiments, invoking can include generating and/or facilitating an APIcall. An API call can be a request to perform one or more processes byan application or a web application. In some embodiments, computersystem 110 may be known as a service requestor or an API requestor.

Application server 115 can be a standalone computing device, amanagement server, a web server, a mobile computing device, or any otherelectronic device or computing system capable of receiving, sending, andprocessing data. In other embodiments, computer system 110 can representa server computing system utilizing multiple computers as a serversystem, such as in a cloud computing environment. In some embodiments,application server 115 can host one or more web applications. In someembodiments, application server 115 can be known as an API provider. Invarious embodiments, application server 115 can be an API provider, anapplication owner, and/or a data processor.

Security module 120 can be any combination of hardware and/or softwareconfigured to identify, protect, and monitor PII, SPI, and/or SI. Insome embodiments, security module 120 can be included in computer system110. In some embodiments, security module 120 is a module of SI manager105. In some embodiments, security module 120 analyzes data to determineif that data is SI. In some embodiments, SI is identified by patternmatching. In some embodiments, security module 120 can be a solicitorservice (e.g. key management server).

In some embodiments, security module 120 generates and providesencryption keys in response to an API call. In some embodiments,security module 120 can provide the encryption key to application server115, allowing decrypting and processing of SI in the API call. Securitymodule 120 includes field key generator 130, usage module 135, anddatabase 140.

Field key generator 130 creates and destroys field keys for theencryption and decryption of SI. In some embodiments, field keygenerator 130 creates an encryption key for SI in an API Call. In someembodiments, field key generator 130 generates one encryption key forall SI in the API call. In some embodiments, field key generator 130generates separate encryption keys for each instance of SI in the APIcall. In some embodiments, each encryption key generated includes anexpiration time. The expiration time is a time after which the key is nolonger valid. In some embodiments, the expiration time is apredetermined period of time. In some embodiments, the expiration timeis based on information provided in the API call. In some embodiments,the expiration time is based on the application in application server115 to which the API call is directed. In some embodiments, theexpiration time is based on the type of SI present in the API call.

In some embodiments, field key generator 130 generates an encryption keyin response to security module 120 identifying SI in the API call. Insome embodiments, field key generator 130 records every action indatabase 140 (e.g. key generated, key destroyed, etc.).

Usage module 135 compiles data and generates reports relating to the useand access to SI. In some embodiments, usage module 135 creates a reportfor a client. The report can include the number of times the client SIwas used in a call (e.g. processed, decrypted, etc.), which webapplications had access to the client SI, failed access attempts to theclient SI, and other similar information related to the client SI. Thereport can be generated upon request, in response to a predeterminedtrigger (e.g. an application request key after expiration) and/or atregular intervals (e.g. weekly, monthly, etc.). In some embodiments,usage module 135 generates reports from data stored in database 140.

Database 140 can be any combination of hardware and/or softwareconfigured to store data for security module 120. In some embodiments,database 140 can store data generated by security module 120, field keygenerator 130, and/or usage module 135. In some embodiments, database140 contains the patterns used to identify SI in API calls.

FIG. 2 depicts a flowchart of an example method for detecting andprotecting sensitive information that can be performed in a computingenvironment (e.g., computing environment 100 and/or computer system110). One or more of the advantages and improvements described above fordetecting and protecting SI can be realized by the method 200,consistent with various embodiments of the present disclosure.

Method 200 can include more or fewer operations than those depicted.Method 200 can include operations in different orders than the orderdepicted. Likewise, the method 200 can include operations that occursimultaneously rather than sequentially. Many modifications to thedepicted method may be made by those skilled in the art withoutdeparting from the spirit and scope of the present disclosure. Method200 can be implemented by one or more processors, a SI manager (e.g., SImanager 105 of FIG. 1), a host computing device (e.g., computer system110 of FIG. 1), or a different combination of hardware and/or software.In various embodiments, the various operations of method 200 areperformed by one or more of SI manager 105, computer system 110,application server 115, security module 120, and/or other computingdevices.

At operation 202, an API call is invoked. In some embodiments, the APIcall is invoked by a user/client through a computing device. In someembodiments, the API call occurs automatically. When invoked, the APIcall includes a set of data to be sent to the API provider, andinstructions on how to process the data. In some embodiments, the datain the API call is categorized under one or more field names. In someembodiments, the API call includes processing by Java script objectnotation (JSON) and/or representational state transfer (REST) methods.

At operation 204, the field names are analyzed. In some embodiments, thedata included in the API call can be organized under various fields eachhaving a unique field name. The number and size of field names isdependent on the API call and the requirements of the entity processingthe API call. In some embodiments, analyzing the field names includesdetermining if the fields have been previously associated with SI. Insome embodiments, the data in the fields that have been previouslyassociated with SI are reformatted to a form acceptable for patternmatching.

At operation 206, SI is identified. In some embodiments, the SI isidentified by security module 120. In some embodiments, the SI isidentified by scanning and/or searching the API for SI. In someembodiments the scanning/searching is performed by a solicitor service.In some embodiments, the scanning/searching is performed by securitymodule 120. In some embodiments, the scanning/searching is performed bySI manager 105. In some embodiments, the data under a field name caninclude one or more instances of SI. In some embodiments, the SI isidentified based on the field name. A field name can be a category ofdata that is always SPI or PII. For example, the field name could be abirthdate, and every entry under the field name can then be consideredSPI.

In some embodiments, the SI is identified by pattern matching. Forexample, a social security number is 9 numbers in length and generallyhas the form: 3 numbers, dash, 2 numbers, dash, 4 numbers (e.g.,123-45-6789). Any set of numbers that has a similar pattern will betreated as PII. In some embodiments, the pattern matching is performedby security module 120.

In some embodiments, searching for SI includes preparing the data forpattern matching. In some embodiments, the data is prepared prior torunning a pattern matching algorithm. This provides security for the SIin the event pattern matching is occurring at a remote location (e.g.security module 120 when the API call is invoked at computer system110). The data can be sent across a network such as network 125 with nochance of having the SI compromised. In some embodiments, the data isprepared by generating a generic form of the data under the field names(e.g., if the data is Dec. 12 1984, then the generic form can be MMM DD,YYYY).

At operation 208, it is determined if SI is present in the API call. Insome embodiments, the determination is based on the results of operation206. If no SI is present in the API call (decision tree “NO” branch)then operation 226 is performed (further described herein). In someembodiments, operation 214 is performed with operation 226, when no SIis present (e.g. processing the API call with no encryption). If SI ispresent in the API call (decision tree “YES” branch) then operation 210is performed.

At operation 210, encryption key(s) (e.g. private signature key,symmetric authentication key, symmetric data encryption key, Triple DataEncryption Standard, RSA, Advanced Encryption Standard (AES), etc.)is/are obtained. In some embodiments, the encryption key is generated bysecurity module 120. In some embodiments, the encryption key isgenerated by field key generator 130. In various embodiments, differentnumbers of keys can be generated for different API calls. For example,there can be one encryption key for the entire API call, a separateencryption key for each field name, or a separate encryption key foreach instance of SI in the API call (e.g. multiple keys under the samefield name). In some embodiments, an expiration is generated with eachencryption key. The expiration can be a period of time (e.g. less thanor equal to 30 seconds, 10 minutes, 30 minutes, 1 hour, 6 hours, etc.),a number of uses (e.g. less than or equal to one use, 5 uses, unlimiteduses etc.), or other similar parameters. In some embodiments, eachgenerated encryption key and its associated expiration are stored indatabase 140.

At operation 212, the SI is encrypted. In some embodiments, the SI isencrypted using the encryption keys generated in operation 210. Atoperation 214, the API request is sent to a processor. In someembodiments, the processor is any computing machine that can process theAPI call. In some embodiments, the API call is sent to applicationserver 115. In some embodiments, a key requestor is sent with the APIcall. The key requestor includes instructions for the recipient on howto obtain the encryption key to process the data.

At operation 216, a request is received for the encryption key. In someembodiments, the request is received from the entity to which the APIcall is sent. In some embodiments, the request is received fromapplication server 115.

At operation 218, it is determined if SI will be used in processing theAPI call. SI is used in processing when the encrypted SI must bedecrypted to fully process the API call. In some embodiments, it isdetermined if SI will be used in processing if SI is present in the APIcall. In some embodiments, data in in the original API call willindicate SI is needed for processing.

In some embodiments, it is determined that SI will be used in processingafter application server 115 attempts to process the API call but cannotcomplete it because of the encryption. In some embodiments, it isdetermined that SI will be used if a request for the encryption key isreceived.

If SI is not used in processing (decision tree “NO” branch) thenoperation 226 is performed. If SI is used in processing (decision tree“YES” branch) then operation 220 is performed.

At operation 220, it is determined if the encryption key is valid. Insome embodiments, the encryption key is valid if it has not expired. Insome embodiments, the encryption key is valid if it has never been used.In some embodiments, the validity of the encryption key can beassociated with a specific processor/entity that is the target of theAPI call. In these embodiments, the target is stored in database 140along with the key at the time the key is generated.

If the key is not valid (decision tree “NO” branch), then operation 224is performed. If the key is valid (decision tree “YES” branch), thenoperation 222 is performed.

At operation 222, the SI is decrypted. In some embodiments, thedecryption is in response to determining the encryption key is valid. Insome embodiments, the decryption is in response to obtaining theencryption key. In some embodiments, the decryption is performed by theprocessor (e.g. application server 115). The encryption key is obtainedby the decrypting party prior to decryption. In some embodiments, theencryption key is obtained from security module 120. In someembodiments, the encryption key is obtained from SI manager 105.

At operation 224, the key usage is recorded. In some embodiments, keyusage includes the request for the key, determination if the SIassociated with the key will be used in processing, whether the key isvalid at the time of the key request, the time of decryption, theprocessor that performed decryption, the number of decryptions, etc.

At operation 226, the API call is processed. In some embodiments, theAPI call is processed by application server 115. In some embodiments,the API call is processed according the invoking instructions.

At operation 228 a usage report is generated. In some embodiments, theusage report is generated by security module 120. In some embodiments,the usage report is generated by usage module 135. In some embodiments,the usage report is generated for an individual client/user. In someembodiments, the usage report can be sent or displayed to the client.Usage reports can be generated after a predetermined period of time(e.g. weekly), after a user requests a report, after each time PII orSPI is processed, or any other trigger. In some embodiments, the usagereport can be generated to show a macro view of SPI and PII usage. Theusage report can show data based on type of PII or SPI, field name, theapplication processing the data, the operator of application server 115,and any other information stored in database 140. For example, one usagereport can be generated that shows each time a social security numberhas been processes by an application owner in the last 30 days.

FIG. 3 illustrates a block diagram of an example SI manager 300 inaccordance with some embodiments of the present disclosure. In someembodiments, SI manager 300 can perform the method 200 as described inFIG. 2. In some embodiments, SI manager 300 provides instructions forthe method 200 of FIG. 2 to a client machine such that the clientmachine executes the method, or a portion of the method, based on theinstructions provided by the SI manager 300.

The SI manager 300 includes a memory 325, storage 330, an interconnect(e.g., BUS) 320, one or more CPUs 305 (also referred to as processors305 herein), an I/O device interface 310, I/O devices 312, and a networkinterface 315.

Each CPU 305 retrieves and executes programming instructions stored inthe memory 325 or storage 330. The interconnect 320 is used to movedata, such as programming instructions, between the CPUs 305, I/O deviceinterface 310, storage 330, network interface 315, and memory 325. Theinterconnect 320 can be implemented using one or more busses. The CPUs305 can be a single CPU, multiple CPUs, or a single CPU having multipleprocessing cores in some embodiments. In some embodiments, CPU 305 canbe a digital signal processor (DSP). In some embodiments, CPU 305includes one or more 3D integrated circuits (3DICs) (e.g., 3Dwafer-level packaging (3DWLP), 3D interposer based integration, 3Dstacked ICs (3D-SICs), monolithic 3D ICs, 3D heterogeneous integration,3D system in package (3DSiP), and/or package on package (PoP CPUconfigurations)). Memory 325 is generally included to be representativeof a nonvolatile memory, such as a hard disk drive, solid state device(SSD), removable memory cards, optical storage, or flash memory devices.In an alternative embodiment, the storage 330 can be replaced by storagearea-network (SAN) deices, the cloud, or other devices connected to theSI manager 300 via the I/O device interface 310 or a network 350 via thenetwork interface 315.

In some embodiments, the memory 325 stores instructions 360 and thestorage 330 stores database 332. However, in some embodiments, theinstructions 360 and database 332 are stored partially in memory 325 andpartially in storage 330, or they are stored entirely in memory 325 orentirely in storage 330, or they are accessed over a network 350 via thenetwork interface 315.

Instructions 360 can be processor-executable instructions for performingany portion of, or all of, any of the method 200 of FIG. 2.

Database 332 can be a storage medium configured to store all actionscompleted by SI manager 300. In some embodiments, database 332 can beconsistent with database 140 of FIG. 1.

In some embodiments, the I/O devices 312 include an interface capable ofpresenting information and receiving input. For example, I/O device 312can present information to a user interacting with SI manager 300 andreceive input from the user.

SI manager 300 is connected to the network 350 via the network interface315. Network 350 can comprise a physical, wireless, cellular, ordifferent network.

Embodiments of the present invention can be a system, a method, and/or acomputer program product at any possible technical detail level ofintegration. The computer program product can include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium can be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network can comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention can be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions can executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer can be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection can be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) can execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instruction can be provided to aprocessor of a general-purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instruction canalso be stored in a computer readable storage medium that can direct acomputer, a programmable data processing apparatus, and/or other devicesto function in a particular manner, such that the computer readablestorage medium having instructions stored therein comprises an articleof manufacture including instructions which implement aspect of thefunction/act specified int eh flowchart and/or block diagram block orblocks.

The computer readable program instruction can also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operations steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to someembodiments of the present invention. In this regard, each block in theflowchart or block diagrams can represent a module, segment, or subsetof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks can occur out of theorder noted in the Figures. For example, two blocks shown in successioncan, in fact, be executed substantially concurrently, or the blocks cansometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While it is understood that the process software (e.g., any of theinstructions stored in instructions 360 of FIG. 3 and/or any softwareconfigured to perform any subset of the methods described with respectto FIG. 2) can be deployed by manually loading it directly in theclient, server, and proxy computers via loading a storage medium such asa CD, DVD, etc., the process software can also be automatically orsemi-automatically deployed into a computer system by sending theprocess software to a central server or a group of central servers. Theprocess software is then downloaded into the client computers that willexecute the process software. Alternatively, the process software issent directly to the client system via e-mail. The process software isthen either detached to a directory or loaded into a directory byexecuting a set of program instructions that detaches the processsoftware into a directory. Another alternative is to send the processsoftware directly to a directory on the client computer hard drive. Whenthere are proxy servers, the process will select the proxy server code,determine on which computers to place the proxy servers' code, transmitthe proxy server code, and then install the proxy server code on theproxy computer. The process software will be transmitted to the proxyserver, and then it will be stored on the proxy server.

Embodiments of the present invention can also be delivered as part of aservice engagement with a client corporation, nonprofit organization,government entity, internal organizational structure, or the like. Theseembodiments can include configuring a computer system to perform, anddeploying software, hardware, and web services that implement, some orall of the methods described herein. These embodiments can also includeanalyzing the client's operations, creating recommendations responsiveto the analysis, building systems that implement subsets of therecommendations, integrating the systems into existing processes andinfrastructure, metering use of the systems, allocating expenses tousers of the systems, and billing, invoicing (e.g., generating aninvoice), or otherwise receiving payment for use of the systems.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 4, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 4 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 5, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 4) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 5 are intended to be illustrative only and embodiments of thedisclosure are not limited thereto. As depicted, the following layersand corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92;encryption key generation 93; data analytics processing 94; transactionprocessing 95; and SI detection and protection 96.

What is claimed is:
 1. A computer implemented method comprising:invoking an application program interface (API) call; determining, inthe API call, a plurality of field names; identifying a first field nameto search for a first instance of sensitive information (SI);identifying the first instance of SI in the first field name by patternmatching; generating, in response to the identifying the first instanceof SI, a first encryption key and a first expiration; encrypting thefirst instance of SI using the first encryption key; sending the APIcall to an application server, wherein the application server isconfigured to process the API call; receiving, at a first time, from theapplication server, a request for the first encryption key; validatingthe first encryption key by determining that the first time is beforethe first expiration; sending, in response to determining the firstencryption key is valid, the first encryption key to the applicationserver; and storing, in a usage database, a set of usage data associatedwith the first encryption key.
 2. The computer implemented method ofclaim 1, wherein the first instance of SI further comprises personallyidentifiable information.
 3. The computer implemented method of claim 1,wherein the first instance of SI further comprises sensitive personalinformation.
 4. The computer implemented method of claim 1, furthercomprising: generating a usage report, wherein the usage reportcomprises the set of usage data associated with the first encryptionkey.
 5. The computer implemented method of claim 4, further comprising:sending the usage report to a first client, wherein the first clientowns the first instance of SI.
 6. The computer implemented method ofclaim 1, wherein the validating further comprises determining theapplication server will use the first instance of SI to process the APIcall.
 7. The computer implemented method of claim 1, wherein the set ofusage data comprises the first instance of SI and the first expiration.8. The computer implemented method of claim 1, further comprising:identifying a second instance of SI; and generating, in response toidentifying the second instance of SI, a second encryption key.
 9. Thecomputer implemented method of claim 8, wherein the second encryptionkey is valid until the first expiration.
 10. The computer implementedmethod of claim 8, wherein a second expiration is generated in responseto generating the second encryption key.